SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

</head>

</h1>

</header>

<p><b>Astronomical Image Processing System</b> <i>++</i> is a software package whose development was started in the early nineties, written almost entirely in <a href="C%2B%2B" title="C++">C++</a>, and which initial goal was to replace the by then already aging <a href="Astronomical_Image_Processing_System" title="Astronomical Image Processing System">AIPS</a> software. It has now been reborn as CASA and is the basis of the image processing systems for several next-generation radio telescopes including <a href="Atacama_Large_Millimeter_Array" title="Atacama Large Millimeter Array">ALMA</a>, <a href="EVLA" class="mw-redirect" title="EVLA">eVLA</a>, and <a href="ASKAP" class="mw-redirect" title="ASKAP">ASKAP</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Early_history">Early history</h2></div>

<p>In 1988-89, the Director of <a href="National_Radio_Astronomy_Observatory" title="National Radio Astronomy Observatory">National Radio Astronomy Observatory</a> (NRAO), Paul Vanden Bout, convened an independent review panel, the Software Advisory Group (SWAG) to produce recommendations for the future of processing software for NRAO. SWAG was chaired by Tim Cornwell, and its members included Geoff Croes, Gareth Hunt, Jan Noordam, and <a href="Ray_Norris_(astrophysicist)" title="Ray Norris (astrophysicist)">Ray Norris</a>. SWAG recommendations were that:

</p>

<ul><li>All data processing in NRAO should be coordinated by a new Assistant Director for Computing</li>

<li>AIPS should be re-designed and re-implemented following certain general guidelines</li>

<li>An equal amount of attention should be devoted to single-dish software.</li></ul>

<p>In late 1990 the NRAO Director accepted the recommendations, and the task of defining the new package began.

</p><p>The project was originally an effort by several astronomical institutes together in a consortium, the <a href="Australia_Telescope_National_Facility" title="Australia Telescope National Facility">Australia Telescope National Facility</a> (ATNF), the <a href="Jodrell_Bank" class="mw-redirect" title="Jodrell Bank">Jodrell Bank</a> Observatory (JBO) and the <a href="MERLIN" title="MERLIN">MERLIN</a>/VLBI National Facility (MERLIN/VLBI), the <a href="Berkeley-Illinois-Maryland_Association" title="Berkeley-Illinois-Maryland Association">Berkeley-Illinois-Maryland Association</a> (<a href="Berkeley-Illinois-Maryland_Association" title="Berkeley-Illinois-Maryland Association">BIMA</a>), the <a href="National_Radio_Astronomy_Observatory" title="National Radio Astronomy Observatory">National Radio Astronomy Observatory</a> (NRAO) and the Netherlands Foundation for Research in Astronomy <a href="ASTRON" title="ASTRON">ASTRON</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Features">Features</h2></div>

<p>AIPS++ provides facilities for calibration, editing, image formation, image enhancement, and analysis of images and other <a href="Astronomy" title="Astronomy">astronomical</a> data. A major focus is on reduction of data from both single-dish and <a href="Aperture_synthesis" title="Aperture synthesis">aperture synthesis</a> <a href="Radio_telescopes" class="mw-redirect" title="Radio telescopes">radio telescopes</a>. Although the tools provided in AIPS++ are mainly designed for processing data from varieties of radio telescopes, the package is expected to also be useful for processing other types of astronomical data and images. However, the reduction of most data from imaging array detectors is performed using <a href="IRAF" title="IRAF">IRAF</a> instead.

</p><p>AIPS++ is structured as a library of tools at the lower levels, designed to replace AIPS of more monolithic applications. In general, the counterpart of an AIPS task is an AIPS++ tool function, although the toolkit structure of AIPS++ will generally mean that these functions are more fine-grained, except for the more integrated tools at the higher levels (such as map). The counterparts of AIPS adverbs are the parameters of AIPS++tool functions. The command-line interpreter in AIPS is POPS, while the counterpart in AIPS++ is <a href="Glish" class="mw-redirect" title="Glish">Glish</a>. The code used as standard in most astronomical institutes is still AIPS, as AIPS++ is usually not yet considered sufficiently reliable and usable.

</p><p>Like most research astronomy software, it is available for all major operating systems except Microsoft Windows.

</p>

<p>On August 25, 2004 the AIPS++ code base was re-organized to a more modular structure; since then it is referred to as CASA ("Common Astronomy Software Applications"). CASA consists of a suite of C++ libraries derived from the original AIPS++ tasks. The Glish scripting system is being replaced by Python bindings, a system known as "CASApy". The CASA software is no longer developed by the consortium, but mainly within NRAO for use on the <a href="Atacama_Large_Millimeter_Array" title="Atacama Large Millimeter Array">Atacama Large Millimeter Array</a>.

</p><p>The core of the old AIPS++ libraries, now known as <a rel="nofollow" class="external text" href="https://github.com/casacore/casacore">CasaCore</a> are still being maintained and developed by the original consortium members. A separate Python interface is available known as <a rel="nofollow" class="external text" href="https://github.com/casacore/python-casacore">python-casacore</a> (formerly "Pyrap"). Python-casacore is mainly developed within ATNF and ASTRON for replacing Glish for the <a href="Australia_Telescope_Compact_Array" title="Australia Telescope Compact Array">Australia Telescope Compact Array</a>, <a href="Westerbork_Synthesis_Radio_Telescope" title="Westerbork Synthesis Radio Telescope">WSRT</a> and <a href="Low-Frequency_Array_(LOFAR)" class="mw-redirect" title="Low-Frequency Array (LOFAR)">LOFAR</a>. CASA also uses these core libraries but not python-casacore.

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070403223632/http://aips2.nrao.edu/docs/project/mission.html">AIPS++ Mission Statement</a></li>

<li>The <a rel="nofollow" class="external text" href="https://web.archive.org/web/20061208101756/http://aips2.nrao.edu/docs/reference/System/System.html">AIPS++ System Manual</a> describes the "nuts & bolts" of the AIPS++ System; how it is put together and how it is intended to run.</li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20030509225259/http://aips2.nrao.edu/docs/cookbook/swdictaips/swdictaips.html">Software Dictionary AIPS/AIPS++</a></li>

<li><a rel="nofollow" class="external text" href="http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=1993ASPC...52..156C&db_key=AST">Croes, G., 1993, "On AIPS++ A New Astronomical Image Processing System"</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070403232130/http://aips2.nrao.edu/docs/aips++.html">AIPS++ homepage</a></li>

<li><a rel="nofollow" class="external text" href="http://casa.nrao.edu/">CASA homepage</a></li>

<li><a rel="nofollow" class="external text" href="news:alt.sci.astro.aips">Usenet newsgroup alt.sci.astro.aips</a></li>

<li><a rel="nofollow" class="external text" href="https://github.com/casacore/casacore">CasaCore</a> and <a rel="nofollow" class="external text" href="https://github.com/casacore/python-casacore">PyRap</a></li>

<li><a rel="nofollow" class="external text" href="http://www.atnf.csiro.au/computing/">Computing at the ATNF</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-03-10" href="https://en.wikipedia.org/wiki/?title=AIPS%2B%2B&oldid=1279746886">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>